Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52c552e6151e88c40200d5d7376facef0d9d48e5181da6a091fcd3972b9c0724

Tx prefix hash: ab7eec42c7a89b34766c9e0375f716c8ff25bdc69bcb4a0f0699e76023f47d24
Tx public key: ade16d3ea18f982cc80afefa4f5dd32c4fe9fbb7bb8c5e955082788ee71bfed8
Timestamp: 1711325719 Timestamp [UCT]: 2024-03-25 00:15:19 Age [y:d:h:m:s]: 00:299:05:21:22
Block: 985662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214171 RingCT/type: yes/0
Extra: 01ade16d3ea18f982cc80afefa4f5dd32c4fe9fbb7bb8c5e955082788ee71bfed80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43b665450882f1f458af570f2c9e426d2e4e07151840618367ea2bf5934cfe4e 0.600000000000 1445879 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": 985672, "vin": [ { "gen": { "height": 985662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43b665450882f1f458af570f2c9e426d2e4e07151840618367ea2bf5934cfe4e" } } ], "extra": [ 1, 173, 225, 109, 62, 161, 143, 152, 44, 200, 10, 254, 250, 79, 93, 211, 44, 79, 233, 251, 183, 187, 140, 94, 149, 80, 130, 120, 142, 231, 27, 254, 216, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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