Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b5f2c7be0b6815116328041b74f513df6e53d72423984e279c4b9ce1aa86e5

Tx prefix hash: 36a67a378103baba9c97e316df6540f5fda35f22a177513b9ac55e34382af57d
Tx public key: 32688eef70f873ab6f1df6c56b8e709030ef7f4acfe6299da36d0dcfefff7e8a
Timestamp: 1756772469 Timestamp [UCT]: 2025-09-02 00:21:09 Age [y:d:h:m:s]: 00:128:15:27:44
Block: 1359444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91981 RingCT/type: yes/0
Extra: 0132688eef70f873ab6f1df6c56b8e709030ef7f4acfe6299da36d0dcfefff7e8a021100000006ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0c6c06a30babe7dd8869bb2f1b72f7bccdb293adceb20affafdbbcc8161103c 0.600000000000 1847457 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": 1359454, "vin": [ { "gen": { "height": 1359444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0c6c06a30babe7dd8869bb2f1b72f7bccdb293adceb20affafdbbcc8161103c" } } ], "extra": [ 1, 50, 104, 142, 239, 112, 248, 115, 171, 111, 29, 246, 197, 107, 142, 112, 144, 48, 239, 127, 74, 207, 230, 41, 157, 163, 109, 13, 207, 239, 255, 126, 138, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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