Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f6c155eb3e23d0e2a18f58ec4593e1f8373dcad70f33b8125f035f1c5f7ca7e

Tx prefix hash: def8cf399022902b7bf1479be41e54a47757a3ec6dd68c200b9a795f5674c271
Tx public key: 273fab1ba3fde86641e6dec4a889bf4d87e837a3cad1f77799f00f09f73c0e50
Timestamp: 1731675066 Timestamp [UCT]: 2024-11-15 12:51:06 Age [y:d:h:m:s]: 00:215:09:41:54
Block: 1154253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153691 RingCT/type: yes/0
Extra: 01273fab1ba3fde86641e6dec4a889bf4d87e837a3cad1f77799f00f09f73c0e50021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b225d19e33a5b413ebc4038d283aea93465cc463f735ff232c09e0c2a50bf225 0.600000000000 1639864 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": 1154263, "vin": [ { "gen": { "height": 1154253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b225d19e33a5b413ebc4038d283aea93465cc463f735ff232c09e0c2a50bf225" } } ], "extra": [ 1, 39, 63, 171, 27, 163, 253, 232, 102, 65, 230, 222, 196, 168, 137, 191, 77, 135, 232, 55, 163, 202, 209, 247, 119, 153, 240, 15, 9, 247, 60, 14, 80, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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