Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac17e312ff3f6df8fbb9d86743c9d2e6e5c1ad411da25b7a9cd1ed5c4c8a61ad

Tx prefix hash: 89e6d42efd6180d38e54a8a2dcd3742739450bdb8d01ac1ec4673129b61160a6
Tx public key: b63be9eb90b8a15745e54eadac362aa857ec81ad335587c7704dbd19133cdcfc
Timestamp: 1724986259 Timestamp [UCT]: 2024-08-30 02:50:59 Age [y:d:h:m:s]: 00:231:19:23:26
Block: 1098888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165551 RingCT/type: yes/0
Extra: 01b63be9eb90b8a15745e54eadac362aa857ec81ad335587c7704dbd19133cdcfc02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b3ae9b65753297a86d0bac4b5789fe8c8a33751c4e76213aedf3a5c42ad2a98 0.600000000000 1574759 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": 1098898, "vin": [ { "gen": { "height": 1098888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b3ae9b65753297a86d0bac4b5789fe8c8a33751c4e76213aedf3a5c42ad2a98" } } ], "extra": [ 1, 182, 59, 233, 235, 144, 184, 161, 87, 69, 229, 78, 173, 172, 54, 42, 168, 87, 236, 129, 173, 51, 85, 135, 199, 112, 77, 189, 25, 19, 60, 220, 252, 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