Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f42c1b0502697fd73fce663861cadb8c0a82307a41ae1a7bd9f2496624144d

Tx prefix hash: ce146a38dedf3ca622e4ffb652ae0198f9fa4f3db01a42ac3102797a816d2779
Tx public key: c301f5191748b56cd9a0cf9a44d02530bef873929ed64b0af99ea9985c932f5d
Timestamp: 1720336010 Timestamp [UCT]: 2024-07-07 07:06:50 Age [y:d:h:m:s]: 00:276:09:33:55
Block: 1060339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197485 RingCT/type: yes/0
Extra: 01c301f5191748b56cd9a0cf9a44d02530bef873929ed64b0af99ea9985c932f5d021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ccbb2be46abea94d586df23a3bb9e14de0c6dd514484f8399434cd69b4fd45 0.600000000000 1530816 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": 1060349, "vin": [ { "gen": { "height": 1060339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ccbb2be46abea94d586df23a3bb9e14de0c6dd514484f8399434cd69b4fd45" } } ], "extra": [ 1, 195, 1, 245, 25, 23, 72, 181, 108, 217, 160, 207, 154, 68, 208, 37, 48, 190, 248, 115, 146, 158, 214, 75, 10, 249, 158, 169, 152, 92, 147, 47, 93, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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