Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a969a38b7ac3bc47eea0697b1e94527c4a4bf67302092ea63682110227979979

Tx prefix hash: 17b0195011cb30499d76db60a8fc2060aef0b652eaa6703a3ae1ef9c405c950c
Tx public key: 3440891531350c3d37e772bdf8450d74f25aab570a09e98214fa4e9dc7cb9a48
Timestamp: 1719148948 Timestamp [UCT]: 2024-06-23 13:22:28 Age [y:d:h:m:s]: 00:284:12:50:14
Block: 1050482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203326 RingCT/type: yes/0
Extra: 013440891531350c3d37e772bdf8450d74f25aab570a09e98214fa4e9dc7cb9a480211000000070fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10994aa204b97d0a4c6f0218396091a3ae5b8103196f04092f06d989e16baeae 0.600000000000 1520655 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": 1050492, "vin": [ { "gen": { "height": 1050482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10994aa204b97d0a4c6f0218396091a3ae5b8103196f04092f06d989e16baeae" } } ], "extra": [ 1, 52, 64, 137, 21, 49, 53, 12, 61, 55, 231, 114, 189, 248, 69, 13, 116, 242, 90, 171, 87, 10, 9, 233, 130, 20, 250, 78, 157, 199, 203, 154, 72, 2, 17, 0, 0, 0, 7, 15, 187, 196, 197, 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