Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55e0241f05ed0ce2321438fecdc74a820637253adbee1f9b3a6704eca4919bc8

Tx prefix hash: df0031b6ea07c7f11c21638e0ec0be83553cfe314c7ccdc446d8ea8c1c554339
Tx public key: 0c79b6444e0c8d9a194afb4c9933feb17c7a7399c3eb3942a787ed1668853ffb
Timestamp: 1725346296 Timestamp [UCT]: 2024-09-03 06:51:36 Age [y:d:h:m:s]: 00:210:20:24:19
Block: 1101879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150527 RingCT/type: yes/0
Extra: 010c79b6444e0c8d9a194afb4c9933feb17c7a7399c3eb3942a787ed1668853ffb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16910295c2d1b0fa2bf2d3c41c4fa0fac7271fc7d53d80c6163500bb2193c063 0.600000000000 1578098 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": 1101889, "vin": [ { "gen": { "height": 1101879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16910295c2d1b0fa2bf2d3c41c4fa0fac7271fc7d53d80c6163500bb2193c063" } } ], "extra": [ 1, 12, 121, 182, 68, 78, 12, 141, 154, 25, 74, 251, 76, 153, 51, 254, 177, 124, 122, 115, 153, 195, 235, 57, 66, 167, 135, 237, 22, 104, 133, 63, 251, 2, 17, 0, 0, 0, 2, 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