Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d8ab287ed14c48901c7f77ec51282ad0fc1b57b3fa8a5b2c1f8bbda5eb5ca50

Tx prefix hash: a07c10754b40e442a9b4d73943b21d742098c42ba6511b1a815dc4957ad47562
Tx public key: ba1add3eb0751fd9ca4fc298eef16ad5bc7a30107d7d8157683f3f07a3a54808
Timestamp: 1737664218 Timestamp [UCT]: 2025-01-23 20:30:18 Age [y:d:h:m:s]: 00:145:06:50:30
Block: 1203799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103582 RingCT/type: yes/0
Extra: 01ba1add3eb0751fd9ca4fc298eef16ad5bc7a30107d7d8157683f3f07a3a54808021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b17ab56cb89e33c7601fec24daa7930a5877a4bc906bbc696a2bf7f269c78f1 0.600000000000 1690478 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": 1203809, "vin": [ { "gen": { "height": 1203799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b17ab56cb89e33c7601fec24daa7930a5877a4bc906bbc696a2bf7f269c78f1" } } ], "extra": [ 1, 186, 26, 221, 62, 176, 117, 31, 217, 202, 79, 194, 152, 238, 241, 106, 213, 188, 122, 48, 16, 125, 125, 129, 87, 104, 63, 63, 7, 163, 165, 72, 8, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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