Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e67ae48753dc48bf7866705974f716ce3a88684d2c15b545e25b1ac4a0bab0

Tx prefix hash: 38aa787f997a2325f3de04ca8047394fa111aec6f3daff7f337863a82c7fb063
Tx public key: 99da72275cea1d7c3453aa7a89f578152c6d8243f6e568e76c08f6aa22534288
Timestamp: 1639344411 Timestamp [UCT]: 2021-12-12 21:26:51 Age [y:d:h:m:s]: 04:009:23:10:18
Block: 394169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1044507 RingCT/type: yes/0
Extra: 0199da72275cea1d7c3453aa7a89f578152c6d8243f6e568e76c08f6aa2253428802110000000375e655a0000000000000000000

1 output(s) for total of 30.335756917000 dcy

stealth address amount amount idx
00: d445d367d6ca3d3281e6d3ab261280772317a7458cf549d217e37f1d4b75259d 30.335756917000 791656 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": 394179, "vin": [ { "gen": { "height": 394169 } } ], "vout": [ { "amount": 30335756917, "target": { "key": "d445d367d6ca3d3281e6d3ab261280772317a7458cf549d217e37f1d4b75259d" } } ], "extra": [ 1, 153, 218, 114, 39, 92, 234, 29, 124, 52, 83, 170, 122, 137, 245, 120, 21, 44, 109, 130, 67, 246, 229, 104, 231, 108, 8, 246, 170, 34, 83, 66, 136, 2, 17, 0, 0, 0, 3, 117, 230, 85, 160, 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