Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 663daf8f0207d0b2a38fe4a52b3b398ed52008a6f82dcad4230dc38afba1f4be

Tx prefix hash: f1e2036dd21375296a8684f11ae9d2e3bffa6d9c9c42ff1043bac87d5f5e04cb
Tx public key: 0449daf3c0470b0ee0300682951758e8017f15627e883c713adcdab2d6495d8b
Timestamp: 1697992863 Timestamp [UCT]: 2023-10-22 16:41:03 Age [y:d:h:m:s]: 01:091:14:55:04
Block: 875305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326686 RingCT/type: yes/0
Extra: 010449daf3c0470b0ee0300682951758e8017f15627e883c713adcdab2d6495d8b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.772238053000 dcy

stealth address amount amount idx
00: e2afcfb2958288bbbdb11fef027a44476dc938e914af363100ce757df2451876 0.772238053000 1330555 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": 875315, "vin": [ { "gen": { "height": 875305 } } ], "vout": [ { "amount": 772238053, "target": { "key": "e2afcfb2958288bbbdb11fef027a44476dc938e914af363100ce757df2451876" } } ], "extra": [ 1, 4, 73, 218, 243, 192, 71, 11, 14, 224, 48, 6, 130, 149, 23, 88, 232, 1, 127, 21, 98, 126, 136, 60, 113, 58, 220, 218, 178, 214, 73, 93, 139, 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