Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8881fca73ae3a85dc16e68eb3340b5f2f21fdfd199dcd3bd1da049ac9d0a865e

Tx prefix hash: eafcb44cb687b64a8cdad949d9d36b249cd043ba848672078e250a9a7f685def
Tx public key: aa03f7e35cfc96ecac3b657f0f7d995a0c285eaf72d7a717efaa2b4851f14fed
Timestamp: 1685481709 Timestamp [UCT]: 2023-05-30 21:21:49 Age [y:d:h:m:s]: 01:296:06:08:08
Block: 771637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472923 RingCT/type: yes/0
Extra: 01aa03f7e35cfc96ecac3b657f0f7d995a0c285eaf72d7a717efaa2b4851f14fed02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.703124783000 dcy

stealth address amount amount idx
00: c6c8bba515ff7a0d9ca382d8e8425aa37f6a8f90e0ed9fbd35f3aefc1336d73f 1.703124783000 1221010 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": 771647, "vin": [ { "gen": { "height": 771637 } } ], "vout": [ { "amount": 1703124783, "target": { "key": "c6c8bba515ff7a0d9ca382d8e8425aa37f6a8f90e0ed9fbd35f3aefc1336d73f" } } ], "extra": [ 1, 170, 3, 247, 227, 92, 252, 150, 236, 172, 59, 101, 127, 15, 125, 153, 90, 12, 40, 94, 175, 114, 215, 167, 23, 239, 170, 43, 72, 81, 241, 79, 237, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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