Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a77e393e687b0770cd410c8410565cd8e1a0a107f4ce392a7d41a7a80e29e4

Tx prefix hash: bc2eb7bef997534db7c0eabc7923a9bc13cd92f96821d5d3fa0d55cbf36c9676
Tx public key: 2106333a45e3e8076593e2b8eb5ea917177bdfd32475ddc6abebe5b651c244ed
Timestamp: 1735697515 Timestamp [UCT]: 2025-01-01 02:11:55 Age [y:d:h:m:s]: 00:102:05:23:42
Block: 1187558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72860 RingCT/type: yes/0
Extra: 012106333a45e3e8076593e2b8eb5ea917177bdfd32475ddc6abebe5b651c244ed0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87abd7c588cc85a1b9e05da46da17e607e97668152c7630e079c2e1a6f0e13af 0.600000000000 1674049 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": 1187568, "vin": [ { "gen": { "height": 1187558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87abd7c588cc85a1b9e05da46da17e607e97668152c7630e079c2e1a6f0e13af" } } ], "extra": [ 1, 33, 6, 51, 58, 69, 227, 232, 7, 101, 147, 226, 184, 235, 94, 169, 23, 23, 123, 223, 211, 36, 117, 221, 198, 171, 235, 229, 182, 81, 194, 68, 237, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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