Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a4b10c9b758df002222591b12cafb0e9f2271cb86ab1212a50d16c7775fd55

Tx prefix hash: f628e9a2277f9379ad60de0c907b87bf526f5c2cf9c83c184f303d3640482591
Tx public key: ba3cc608a2ecebf0f05194e0751c8dea2c8cae3f21f7e0e7fd4d725914ca45f8
Timestamp: 1749301051 Timestamp [UCT]: 2025-06-07 12:57:31 Age [y:d:h:m:s]: 00:159:06:52:59
Block: 1299930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111508 RingCT/type: yes/0
Extra: 01ba3cc608a2ecebf0f05194e0751c8dea2c8cae3f21f7e0e7fd4d725914ca45f8021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba8a7512f696b76fea771737850c1b4e91e3fb929ef1a592e388d7b7aa692091 0.600000000000 1787473 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": 1299940, "vin": [ { "gen": { "height": 1299930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba8a7512f696b76fea771737850c1b4e91e3fb929ef1a592e388d7b7aa692091" } } ], "extra": [ 1, 186, 60, 198, 8, 162, 236, 235, 240, 240, 81, 148, 224, 117, 28, 141, 234, 44, 140, 174, 63, 33, 247, 224, 231, 253, 77, 114, 89, 20, 202, 69, 248, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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