Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88c526e1f24df6b59398667452217b07750bf7f84a19d65016dd64f8cc530015

Tx prefix hash: 4f59385c419c8b95c95932160277ed030d7ad590a40963eb1bf7666a2a340e00
Tx public key: 4920a9d6041e6ae699881e686d8b979468e2b44d3b5a6215c9c0d843037a658b
Timestamp: 1737312831 Timestamp [UCT]: 2025-01-19 18:53:51 Age [y:d:h:m:s]: 00:299:02:36:59
Block: 1200923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211293 RingCT/type: yes/0
Extra: 014920a9d6041e6ae699881e686d8b979468e2b44d3b5a6215c9c0d843037a658b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b1fe629532f9d940841bdacaad7c757ea0e3e423963d68eccbeb2421d23d9b8 0.600000000000 1687570 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": 1200933, "vin": [ { "gen": { "height": 1200923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b1fe629532f9d940841bdacaad7c757ea0e3e423963d68eccbeb2421d23d9b8" } } ], "extra": [ 1, 73, 32, 169, 214, 4, 30, 106, 230, 153, 136, 30, 104, 109, 139, 151, 148, 104, 226, 180, 77, 59, 90, 98, 21, 201, 192, 216, 67, 3, 122, 101, 139, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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