Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa1eb1edc543623ad24ebd32932981ac9216cb5e295c1acf4869957e6d690231

Tx prefix hash: f3e94436555f68863ffc33d8df9b47b969bbcc584e95a3da7682d8c9c8153dac
Tx public key: af271e7a61d72bd69d386ae00c377bfe4edb5d88c19b633d31522913cc8bdbd3
Timestamp: 1639284906 Timestamp [UCT]: 2021-12-12 04:55:06 Age [y:d:h:m:s]: 02:348:10:46:40
Block: 393675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767116 RingCT/type: yes/0
Extra: 01af271e7a61d72bd69d386ae00c377bfe4edb5d88c19b633d31522913cc8bdbd3021100000001117daff0000000000000000000

1 output(s) for total of 30.450306150000 dcy

stealth address amount amount idx
00: b164d077f9edd07a9f2cff92fc5c93706cd23799c995c00087924f341cefddbd 30.450306150000 790986 of 0

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": 393685, "vin": [ { "gen": { "height": 393675 } } ], "vout": [ { "amount": 30450306150, "target": { "key": "b164d077f9edd07a9f2cff92fc5c93706cd23799c995c00087924f341cefddbd" } } ], "extra": [ 1, 175, 39, 30, 122, 97, 215, 43, 214, 157, 56, 106, 224, 12, 55, 123, 254, 78, 219, 93, 136, 193, 155, 99, 61, 49, 82, 41, 19, 204, 139, 219, 211, 2, 17, 0, 0, 0, 1, 17, 125, 175, 240, 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