Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63043cb893fb9ce1c1fb9eece6ea43b1109dfadd7cb8303e7c01f32213adf00b

Tx prefix hash: efa79a25b5744f6dced829b74ad61b39854af129fa09bbfbf03e2ff617c9193f
Tx public key: f523880c5d6580af8189a86cc84036f719518f25e3ca4cdd974a3fcd70d97ee5
Timestamp: 1703461115 Timestamp [UCT]: 2023-12-24 23:38:35 Age [y:d:h:m:s]: 01:139:23:02:26
Block: 920449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361154 RingCT/type: yes/0
Extra: 01f523880c5d6580af8189a86cc84036f719518f25e3ca4cdd974a3fcd70d97ee502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49314adfadbb23c9daf0e507497843d1719f8cb3799ad56e63853fd07e7ecb8e 0.600000000000 1378127 of 15

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": 920459, "vin": [ { "gen": { "height": 920449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49314adfadbb23c9daf0e507497843d1719f8cb3799ad56e63853fd07e7ecb8e" } } ], "extra": [ 1, 245, 35, 136, 12, 93, 101, 128, 175, 129, 137, 168, 108, 200, 64, 54, 247, 25, 81, 143, 37, 227, 202, 76, 221, 151, 74, 63, 205, 112, 217, 126, 229, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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