Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7e5039189d20fdc145390587da1b5710873254b1e19856824c954ade259e562e

Tx prefix hash: ebef1608875b24eb6fdc492071335a20e9544a0db93dc0bff1566f81c666a919
Tx public key: d2b7194d10ec8f03ab912acfb4a322589f636f0c57dcfe5aaf48eba525d50954
Timestamp: 1703997643 Timestamp [UCT]: 2023-12-31 04:40:43 Age [y:d:h:m:s]: 01:156:21:48:11
Block: 924878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373312 RingCT/type: yes/0
Extra: 01d2b7194d10ec8f03ab912acfb4a322589f636f0c57dcfe5aaf48eba525d509540211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b244872a28307ad68f7e23fa4331a1a1c04084d631c8847eb0256acbbb479a23 0.600000000000 1382638 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 924888, "vin": [ { "gen": { "height": 924878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b244872a28307ad68f7e23fa4331a1a1c04084d631c8847eb0256acbbb479a23" } } ], "extra": [ 1, 210, 183, 25, 77, 16, 236, 143, 3, 171, 145, 42, 207, 180, 163, 34, 88, 159, 99, 111, 12, 87, 220, 254, 90, 175, 72, 235, 165, 37, 213, 9, 84, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8