Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f08c5bda69759d3cd575b3ae4cbcf6b711597220f26c5ad03502fa2fbcdf954

Tx prefix hash: b2070fb3ecbbdacc175d6978dc479ad6ac2b6dec11b9f02b12dd7cf046dbc0d3
Tx public key: 6f055f33d14f1762de3f158bdecfdcee4f80ac54c81cda956037ecb88d203bb8
Timestamp: 1736969140 Timestamp [UCT]: 2025-01-15 19:25:40 Age [y:d:h:m:s]: 00:308:12:35:49
Block: 1198084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218021 RingCT/type: yes/0
Extra: 016f055f33d14f1762de3f158bdecfdcee4f80ac54c81cda956037ecb88d203bb80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a64378b6899dfad1fa21a8c59e047559f979f2867e327b065fe719001c6a5b0b 0.600000000000 1684703 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": 1198094, "vin": [ { "gen": { "height": 1198084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a64378b6899dfad1fa21a8c59e047559f979f2867e327b065fe719001c6a5b0b" } } ], "extra": [ 1, 111, 5, 95, 51, 209, 79, 23, 98, 222, 63, 21, 139, 222, 207, 220, 238, 79, 128, 172, 84, 200, 28, 218, 149, 96, 55, 236, 184, 141, 32, 59, 184, 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