Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81327b7148120d92552bd273a49ac2bdf05ecc562df34bf1a477ee77b3e6014b

Tx prefix hash: ce767be44b65a1fcb9f6d98ca47229e196d97854af95454af43b9647254192f7
Tx public key: a3eeb1431855e67e4cb0f719932b0f58350bb16ba6aad5b6e825ade3e0b8c08b
Timestamp: 1697470276 Timestamp [UCT]: 2023-10-16 15:31:16 Age [y:d:h:m:s]: 01:217:12:57:03
Block: 870967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416551 RingCT/type: yes/0
Extra: 01a3eeb1431855e67e4cb0f719932b0f58350bb16ba6aad5b6e825ade3e0b8c08b021100000001faf35c9c000000000000000000

1 output(s) for total of 0.798224033000 dcy

stealth address amount amount idx
00: 4c513addc2a6d3b681462d21a1483b5afb3aa8e656984f2c3654a09eae7c7936 0.798224033000 1325934 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": 870977, "vin": [ { "gen": { "height": 870967 } } ], "vout": [ { "amount": 798224033, "target": { "key": "4c513addc2a6d3b681462d21a1483b5afb3aa8e656984f2c3654a09eae7c7936" } } ], "extra": [ 1, 163, 238, 177, 67, 24, 85, 230, 126, 76, 176, 247, 25, 147, 43, 15, 88, 53, 11, 177, 107, 166, 170, 213, 182, 232, 37, 173, 227, 224, 184, 192, 139, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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