Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c0e76b886d3a8d8a0b1909fac4c01816a368cf0a4f88af87a871868f0d221dc

Tx prefix hash: c07cd1761d3600ba3e9d526b2b17aaa0832a673b75655f039a9a4986fc43486e
Tx public key: 83f749e9f7958450949ca802c1c0d3f0add79dba5e18bcd7b12d87bd8d984b42
Timestamp: 1728645928 Timestamp [UCT]: 2024-10-11 11:25:28 Age [y:d:h:m:s]: 01:030:11:57:10
Block: 1129236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280167 RingCT/type: yes/0
Extra: 0183f749e9f7958450949ca802c1c0d3f0add79dba5e18bcd7b12d87bd8d984b4202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec82ff6ce96f35175a24db5bc6ee482c16b57ae14275bca9531025e8ddb96b0 0.600000000000 1612061 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": 1129246, "vin": [ { "gen": { "height": 1129236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec82ff6ce96f35175a24db5bc6ee482c16b57ae14275bca9531025e8ddb96b0" } } ], "extra": [ 1, 131, 247, 73, 233, 247, 149, 132, 80, 148, 156, 168, 2, 193, 192, 211, 240, 173, 215, 157, 186, 94, 24, 188, 215, 177, 45, 135, 189, 141, 152, 75, 66, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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