Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17496ef793c1d3ae501983af213939c09b57fdb3dfeb62acf071f097d24d0f6a

Tx prefix hash: 4ab3b9fa08ed3383f33ba95fece33fb33bdc7b2a8735aadcef203d0498cd9206
Tx public key: d5a63edd299ef3bfd561fc25e833ff19fa85650d4ee3e37632922932ed19d1b0
Timestamp: 1737698320 Timestamp [UCT]: 2025-01-24 05:58:40 Age [y:d:h:m:s]: 00:144:10:18:27
Block: 1204088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102972 RingCT/type: yes/0
Extra: 01d5a63edd299ef3bfd561fc25e833ff19fa85650d4ee3e37632922932ed19d1b00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d544c1f4ccc20903a81b628d1eb5ae3f8e37e557b0f4a92d831fd27f6f1ba7a6 0.600000000000 1690771 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": 1204098, "vin": [ { "gen": { "height": 1204088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d544c1f4ccc20903a81b628d1eb5ae3f8e37e557b0f4a92d831fd27f6f1ba7a6" } } ], "extra": [ 1, 213, 166, 62, 221, 41, 158, 243, 191, 213, 97, 252, 37, 232, 51, 255, 25, 250, 133, 101, 13, 78, 227, 227, 118, 50, 146, 41, 50, 237, 25, 209, 176, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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