Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ae5294461ab0a558ac168f3df7a2c293ed927b7a91c1bbfb49fc67733a279c

Tx prefix hash: 710e145c9a301ae6eef2e814d2b0b01e1589255df607e031097458a18828efa7
Tx public key: 792bb54d7a56aa714500e5d7b7476ba65a07ece33574dcc28a778f5b45d80732
Timestamp: 1760448128 Timestamp [UCT]: 2025-10-14 13:22:08 Age [y:d:h:m:s]: 00:028:13:38:50
Block: 1389770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20456 RingCT/type: yes/0
Extra: 01792bb54d7a56aa714500e5d7b7476ba65a07ece33574dcc28a778f5b45d80732021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b1195e835535e5d31cb3871edebe6e7d38dca6e5a1c5942bcd1a0aae77c8bd2 0.600000000000 1877999 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": 1389780, "vin": [ { "gen": { "height": 1389770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b1195e835535e5d31cb3871edebe6e7d38dca6e5a1c5942bcd1a0aae77c8bd2" } } ], "extra": [ 1, 121, 43, 181, 77, 122, 86, 170, 113, 69, 0, 229, 215, 183, 71, 107, 166, 90, 7, 236, 227, 53, 116, 220, 194, 138, 119, 143, 91, 69, 216, 7, 50, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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