Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c8f89fe0c3f1b456d13f18b4fc37c6d084f53b645bb00803c2dc44eeeb4a85

Tx prefix hash: 11e6e2a07025816aba58e9f68502a627aa291e3e11877b573f0485a717c13b5d
Tx public key: 9e32f187eefaedcd75e3594d6db5a562428d610f1146904336048ddbe319b8a0
Timestamp: 1719509656 Timestamp [UCT]: 2024-06-27 17:34:16 Age [y:d:h:m:s]: 01:136:12:51:20
Block: 1053484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356127 RingCT/type: yes/0
Extra: 019e32f187eefaedcd75e3594d6db5a562428d610f1146904336048ddbe319b8a00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6db3c46ffee253d251c18ed41da3f86641a5af1b971ddae6b6ba77cd57f4e6e2 0.600000000000 1523831 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": 1053494, "vin": [ { "gen": { "height": 1053484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6db3c46ffee253d251c18ed41da3f86641a5af1b971ddae6b6ba77cd57f4e6e2" } } ], "extra": [ 1, 158, 50, 241, 135, 238, 250, 237, 205, 117, 227, 89, 77, 109, 181, 165, 98, 66, 141, 97, 15, 17, 70, 144, 67, 54, 4, 141, 219, 227, 25, 184, 160, 2, 17, 0, 0, 0, 2, 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