Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fe029d13c651b4b5fcfcc8134851a043207bf0e2cd35bee725d2e9677165908

Tx prefix hash: 23e72fa046c28480c1e19ae0318ae732f08598376bc598f8e3daa839a8368c1d
Tx public key: b2cb67ddb6acc5702eeeedc1114725c15262df29e95dd0ae52ce6c63be79acc6
Timestamp: 1578950959 Timestamp [UCT]: 2020-01-13 21:29:19 Age [y:d:h:m:s]: 04:312:04:41:08
Block: 44978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112540 RingCT/type: yes/0
Extra: 01b2cb67ddb6acc5702eeeedc1114725c15262df29e95dd0ae52ce6c63be79acc60211000000344943cd9f000000000000000000

1 output(s) for total of 435.481845865000 dcy

stealth address amount amount idx
00: eb4add99cb4f778744d58cd5350fe7cc6d01ada1abb714d9a8a0fac366123c29 435.481845865000 82024 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": 44988, "vin": [ { "gen": { "height": 44978 } } ], "vout": [ { "amount": 435481845865, "target": { "key": "eb4add99cb4f778744d58cd5350fe7cc6d01ada1abb714d9a8a0fac366123c29" } } ], "extra": [ 1, 178, 203, 103, 221, 182, 172, 197, 112, 46, 238, 237, 193, 17, 71, 37, 193, 82, 98, 223, 41, 233, 93, 208, 174, 82, 206, 108, 99, 190, 121, 172, 198, 2, 17, 0, 0, 0, 52, 73, 67, 205, 159, 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