Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1643c899784121d1775957fad4ea50c2dc683f624eae2690a9f530951af0310b

Tx prefix hash: 905e6ff88446107eb6b2909ca8a15af373015b458aba9530bf77aa30a346dda0
Tx public key: 0a69f6f2f13ff70a753b7231e708f7f94d1b6d1c5a70bb3f0a4df093718919d2
Timestamp: 1744984498 Timestamp [UCT]: 2025-04-18 13:54:58 Age [y:d:h:m:s]: 00:216:08:32:22
Block: 1264184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152346 RingCT/type: yes/0
Extra: 010a69f6f2f13ff70a753b7231e708f7f94d1b6d1c5a70bb3f0a4df093718919d20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08be924de957ca29546bf6d1ee8bddd121beeef80e3043ee326de44bba88919b 0.600000000000 1751379 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": 1264194, "vin": [ { "gen": { "height": 1264184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08be924de957ca29546bf6d1ee8bddd121beeef80e3043ee326de44bba88919b" } } ], "extra": [ 1, 10, 105, 246, 242, 241, 63, 247, 10, 117, 59, 114, 49, 231, 8, 247, 249, 77, 27, 109, 28, 90, 112, 187, 63, 10, 77, 240, 147, 113, 137, 25, 210, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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