Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dc24b40f2765664cf952202adaa80a8f98eb57eaa44d388153c2e39352fd4a4

Tx prefix hash: 3e18f73cc80ed5664fb25e44d9102f1b5871fd495fa17b08b5c643022f88e2ad
Tx public key: 0a45221b04211bad19ae7abade0057a06cdf83d2af3e1da0a435d7d4a15182b7
Timestamp: 1753265910 Timestamp [UCT]: 2025-07-23 10:18:30 Age [y:d:h:m:s]: 00:120:07:12:18
Block: 1331583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84797 RingCT/type: yes/0
Extra: 010a45221b04211bad19ae7abade0057a06cdf83d2af3e1da0a435d7d4a15182b702110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d51267c5243bae7bbcd614305e06c6ae9df531044c7bf6431b4945b9526d4a6 0.600000000000 1819378 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": 1331593, "vin": [ { "gen": { "height": 1331583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d51267c5243bae7bbcd614305e06c6ae9df531044c7bf6431b4945b9526d4a6" } } ], "extra": [ 1, 10, 69, 34, 27, 4, 33, 27, 173, 25, 174, 122, 186, 222, 0, 87, 160, 108, 223, 131, 210, 175, 62, 29, 160, 164, 53, 215, 212, 161, 81, 130, 183, 2, 17, 0, 0, 0, 8, 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