Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3490db99616db2efe8f76f6dfec9a66ea60986cee4052cafee2178ed08f6b9cd

Tx prefix hash: 008da96b4435a72f28f2576ed84a57b7c7e620b02371412eafe7ad5f982674b0
Tx public key: 1453a42b3405fb4730d1f8da106cb01cfe9589cbc4a907d4f44cc494059ff0f9
Timestamp: 1713247147 Timestamp [UCT]: 2024-04-16 05:59:07 Age [y:d:h:m:s]: 00:315:18:21:15
Block: 1001551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225731 RingCT/type: yes/0
Extra: 011453a42b3405fb4730d1f8da106cb01cfe9589cbc4a907d4f44cc494059ff0f902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1001e54e9a05614c6893666be1d6a86bd048bc19744fdd5e94f092090a208807 0.600000000000 1462057 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": 1001561, "vin": [ { "gen": { "height": 1001551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1001e54e9a05614c6893666be1d6a86bd048bc19744fdd5e94f092090a208807" } } ], "extra": [ 1, 20, 83, 164, 43, 52, 5, 251, 71, 48, 209, 248, 218, 16, 108, 176, 28, 254, 149, 137, 203, 196, 169, 7, 212, 244, 76, 196, 148, 5, 159, 240, 249, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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