Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4066ff1da89284565df222e3234afa9fcb1b6e567dfded7f1c24c9b3db5ebe2

Tx prefix hash: 589791e8fc5daf6519302d3c8a891fb1e242de45ffb0dde3b3d1da817926e28c
Tx public key: db88db2de9d1daee967ac712f1fca4248dcacc5fb262487909b87844d535a84a
Timestamp: 1749334152 Timestamp [UCT]: 2025-06-07 22:09:12 Age [y:d:h:m:s]: 00:161:06:21:53
Block: 1300198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112941 RingCT/type: yes/0
Extra: 01db88db2de9d1daee967ac712f1fca4248dcacc5fb262487909b87844d535a84a02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b81da41700a6f99a644eab5b3e336b4ec26e7f6ba2134c1389d71f5cfcc6b2a3 0.600000000000 1787747 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": 1300208, "vin": [ { "gen": { "height": 1300198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b81da41700a6f99a644eab5b3e336b4ec26e7f6ba2134c1389d71f5cfcc6b2a3" } } ], "extra": [ 1, 219, 136, 219, 45, 233, 209, 218, 238, 150, 122, 199, 18, 241, 252, 164, 36, 141, 202, 204, 95, 178, 98, 72, 121, 9, 184, 120, 68, 213, 53, 168, 74, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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