Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c12576301ee55cbc9306e2f6f933463345e40054cb6d31813495da483613df3

Tx prefix hash: e006f643c9827ed3fc4b23bd9e4abed95c39b2f0103e8f54fcc3365c1179650a
Tx public key: a434cc80fe286d4ca4cb1e93cfc538b8764c6efc377d6f6baa54ce4004a7efef
Timestamp: 1681702119 Timestamp [UCT]: 2023-04-17 03:28:39 Age [y:d:h:m:s]: 01:277:09:33:26
Block: 740279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459787 RingCT/type: yes/0
Extra: 01a434cc80fe286d4ca4cb1e93cfc538b8764c6efc377d6f6baa54ce4004a7efef021100000001faf35c9c000000000000000000

1 output(s) for total of 2.163458585000 dcy

stealth address amount amount idx
00: 56ff28e0ffdb814789bc1a911e414b367e9c97bba6894eb3cf9e98f40ca8a195 2.163458585000 1187170 of 0

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": 740289, "vin": [ { "gen": { "height": 740279 } } ], "vout": [ { "amount": 2163458585, "target": { "key": "56ff28e0ffdb814789bc1a911e414b367e9c97bba6894eb3cf9e98f40ca8a195" } } ], "extra": [ 1, 164, 52, 204, 128, 254, 40, 109, 76, 164, 203, 30, 147, 207, 197, 56, 184, 118, 76, 110, 252, 55, 125, 111, 107, 170, 84, 206, 64, 4, 167, 239, 239, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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