Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c7cd8d70934e031a54cb3d5017fe57f72a9a16fe8ad5031ed235186ff511cb4

Tx prefix hash: c08e89c7c3ba18da5ef93a203467be61a71cdbcee249e83dbbc588322d91fc79
Tx public key: 95607bfccfda28b84d33af561fdcbe0eebdfac13a396d27ef17c9d3a9a34d235
Timestamp: 1728494383 Timestamp [UCT]: 2024-10-09 17:19:43 Age [y:d:h:m:s]: 00:232:21:51:20
Block: 1127974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166304 RingCT/type: yes/0
Extra: 0195607bfccfda28b84d33af561fdcbe0eebdfac13a396d27ef17c9d3a9a34d23502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd6ba055b1e9f9228f7fe8ae7fd9709e5e028fdfd631d080548785c52f716d8c 0.600000000000 1610789 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": 1127984, "vin": [ { "gen": { "height": 1127974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd6ba055b1e9f9228f7fe8ae7fd9709e5e028fdfd631d080548785c52f716d8c" } } ], "extra": [ 1, 149, 96, 123, 252, 207, 218, 40, 184, 77, 51, 175, 86, 31, 220, 190, 14, 235, 223, 172, 19, 163, 150, 210, 126, 241, 124, 157, 58, 154, 52, 210, 53, 2, 17, 0, 0, 0, 7, 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