Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53719def10abefb55f62c7426dfcdb7255e766599aa280e1ebf09e7549880274

Tx prefix hash: 264755ef4fe18f4d8067878cb19e55df3338cb93cccdeb2690da530d3d5a3190
Tx public key: 7c83637766a260f1432ad415f4f4acf39fbd6f763f9ef50f0848eb53cb2b8fdf
Timestamp: 1734105802 Timestamp [UCT]: 2024-12-13 16:03:22 Age [y:d:h:m:s]: 00:101:20:52:26
Block: 1174418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72569 RingCT/type: yes/0
Extra: 017c83637766a260f1432ad415f4f4acf39fbd6f763f9ef50f0848eb53cb2b8fdf0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f32c14758875a90d33e6b15de343ddc0e5ade07acbe1d5e55f593058ae2f2541 0.600000000000 1660567 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": 1174428, "vin": [ { "gen": { "height": 1174418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f32c14758875a90d33e6b15de343ddc0e5ade07acbe1d5e55f593058ae2f2541" } } ], "extra": [ 1, 124, 131, 99, 119, 102, 162, 96, 241, 67, 42, 212, 21, 244, 244, 172, 243, 159, 189, 111, 118, 63, 158, 245, 15, 8, 72, 235, 83, 203, 43, 143, 223, 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