Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34febf1cc74325e3bd57b85e9feff0fe4b98e6e3004463120933e7a88486cf15

Tx prefix hash: f8e46a5be69191ad2461ae36ad1e631e8bdb054a450bad17201037eaad4e9d67
Tx public key: 76e2beda9766a4137b77de8cec52283b6fe65076624badf993e0a9b41ee5c5ea
Timestamp: 1759147875 Timestamp [UCT]: 2025-09-29 12:11:15 Age [y:d:h:m:s]: 00:008:15:25:06
Block: 1378999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6177 RingCT/type: yes/0
Extra: 0176e2beda9766a4137b77de8cec52283b6fe65076624badf993e0a9b41ee5c5ea021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77c509e7a70b8fc5b3b86b0fd0e52dd7910d2dcc695f2aff5836867f4a11a7a 0.600000000000 1867096 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": 1379009, "vin": [ { "gen": { "height": 1378999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77c509e7a70b8fc5b3b86b0fd0e52dd7910d2dcc695f2aff5836867f4a11a7a" } } ], "extra": [ 1, 118, 226, 190, 218, 151, 102, 164, 19, 123, 119, 222, 140, 236, 82, 40, 59, 111, 230, 80, 118, 98, 75, 173, 249, 147, 224, 169, 180, 30, 229, 197, 234, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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