Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b912c03e6200b1a926c72d96ccf1f145d0ecd36a43c92c48e32c9db6cae8a6ea

Tx prefix hash: 08d1e72934ba75e4e077b097125c63f379c5eba84146026619ef6c2077aba510
Tx public key: f889ce84c24aa2b4646c17894af16581468738084ea9a199e60ad5f36e9d735e
Timestamp: 1669657741 Timestamp [UCT]: 2022-11-28 17:49:01 Age [y:d:h:m:s]: 02:137:02:19:02
Block: 641097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619696 RingCT/type: yes/0
Extra: 01f889ce84c24aa2b4646c17894af16581468738084ea9a199e60ad5f36e9d735e02110000000133af99f4000000000000000000

1 output(s) for total of 4.610834208000 dcy

stealth address amount amount idx
00: 246e24f5ade8d740416349f307247935cc0bffdbe69c250dd14f1c0a258c4d5d 4.610834208000 1080872 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": 641107, "vin": [ { "gen": { "height": 641097 } } ], "vout": [ { "amount": 4610834208, "target": { "key": "246e24f5ade8d740416349f307247935cc0bffdbe69c250dd14f1c0a258c4d5d" } } ], "extra": [ 1, 248, 137, 206, 132, 194, 74, 162, 180, 100, 108, 23, 137, 74, 241, 101, 129, 70, 135, 56, 8, 78, 169, 161, 153, 230, 10, 213, 243, 110, 157, 115, 94, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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