Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9449af932d1a750bdbd0fd44c0e58b84a0cbd495262ced2efcb2c1d6a3f7c31a

Tx prefix hash: 3e154d2bdc3b32d164e8d34afa08587ff178f6fa503a06cd1c885251003473ab
Tx public key: f0a7de6c280189582b4b2d2df9f5c6638dfd8adfb8a67e2dfa5c97222988eaf5
Timestamp: 1713799899 Timestamp [UCT]: 2024-04-22 15:31:39 Age [y:d:h:m:s]: 00:325:15:39:59
Block: 1006157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232800 RingCT/type: yes/0
Extra: 01f0a7de6c280189582b4b2d2df9f5c6638dfd8adfb8a67e2dfa5c97222988eaf502110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffaa5643b03ca43646f99de247c0047dbe802df087c3892a8b6c1e60ebe1aca4 0.600000000000 1467091 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": 1006167, "vin": [ { "gen": { "height": 1006157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffaa5643b03ca43646f99de247c0047dbe802df087c3892a8b6c1e60ebe1aca4" } } ], "extra": [ 1, 240, 167, 222, 108, 40, 1, 137, 88, 43, 75, 45, 45, 249, 245, 198, 99, 141, 253, 138, 223, 184, 166, 126, 45, 250, 92, 151, 34, 41, 136, 234, 245, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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