Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a38fdb51b5c14a7a1d92fe7124c66d5ebdff567a3dc2acaec11e40c783c29ca1

Tx prefix hash: 59dddceabac7407f6e30961a87c3a6ad93fb4db3aeae0a9d97282e633f7571f1
Tx public key: d8403b5f3db72112a1a006ba32cf0ed527775e9dd6f6e886851770445733233c
Timestamp: 1705551663 Timestamp [UCT]: 2024-01-18 04:21:03 Age [y:d:h:m:s]: 01:099:18:57:01
Block: 937739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332446 RingCT/type: yes/0
Extra: 01d8403b5f3db72112a1a006ba32cf0ed527775e9dd6f6e886851770445733233c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 219aee1f3f50c443733bd376080f7e1d9f47369fceddf3997a6d3f40c6088f5d 0.600000000000 1395801 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": 937749, "vin": [ { "gen": { "height": 937739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "219aee1f3f50c443733bd376080f7e1d9f47369fceddf3997a6d3f40c6088f5d" } } ], "extra": [ 1, 216, 64, 59, 95, 61, 183, 33, 18, 161, 160, 6, 186, 50, 207, 14, 213, 39, 119, 94, 157, 214, 246, 232, 134, 133, 23, 112, 68, 87, 51, 35, 60, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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