Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bd440b38734586a2a0e85b8f52c0fe771a413cff147bd891813d851ef100fff

Tx prefix hash: a74cb41f538e61d7bf03778235c0d20180c80853ece9c801c34b9737e4ed2a8e
Tx public key: e2a0d63ecb40cf084b7f2cf38d50a6476bf38dad9be0203d4e9939b9986160dd
Timestamp: 1649018802 Timestamp [UCT]: 2022-04-03 20:46:42 Age [y:d:h:m:s]: 02:344:09:30:47
Block: 472537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 765684 RingCT/type: yes/0
Extra: 01e2a0d63ecb40cf084b7f2cf38d50a6476bf38dad9be0203d4e9939b9986160dd02110000000da8c141c5000000000000000000

1 output(s) for total of 16.683570670000 dcy

stealth address amount amount idx
00: 692ca7f5f094ab0301aca97c57dc9cd998f9df69215ba43fb31dc4a14cde678a 16.683570670000 892152 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": 472547, "vin": [ { "gen": { "height": 472537 } } ], "vout": [ { "amount": 16683570670, "target": { "key": "692ca7f5f094ab0301aca97c57dc9cd998f9df69215ba43fb31dc4a14cde678a" } } ], "extra": [ 1, 226, 160, 214, 62, 203, 64, 207, 8, 75, 127, 44, 243, 141, 80, 166, 71, 107, 243, 141, 173, 155, 224, 32, 61, 78, 153, 57, 185, 152, 97, 96, 221, 2, 17, 0, 0, 0, 13, 168, 193, 65, 197, 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