Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ab03b29264a25786155c0c956b9b7cc1ef4dff1745c70e3648186d4f0cafb6d

Tx prefix hash: 47e6f1849e595c3b6a0cf51050a98738b7ab53019597f2bb8fca597046cb4ead
Tx public key: 09273a9fc25fb0f9bed38417ad3e3fba6cd4277a6af3caae45a6a366017ab508
Timestamp: 1764410734 Timestamp [UCT]: 2025-11-29 10:05:34 Age [y:d:h:m:s]: 00:065:03:05:32
Block: 1422621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46443 RingCT/type: yes/0
Extra: 0109273a9fc25fb0f9bed38417ad3e3fba6cd4277a6af3caae45a6a366017ab50802110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c23e8ec7080aac4de3363237a115bba9ed4b3c8677a5d2432cb39ef31b577b82 0.600000000000 1911190 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": 1422631, "vin": [ { "gen": { "height": 1422621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c23e8ec7080aac4de3363237a115bba9ed4b3c8677a5d2432cb39ef31b577b82" } } ], "extra": [ 1, 9, 39, 58, 159, 194, 95, 176, 249, 190, 211, 132, 23, 173, 62, 63, 186, 108, 212, 39, 122, 106, 243, 202, 174, 69, 166, 163, 102, 1, 122, 181, 8, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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