Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d06f9002b0de8f88033d02e68ba2cbc338c73947a64435e99f7fbf07f423032e

Tx prefix hash: 0748ecccaffcb52c50cfc11589d53d18fc22d7fabd0f1208dbd1e40a8ad1fad7
Tx public key: 4887ac4072c78bf7e7a2a10a34c5a183fab652211da71ff50564821cf4df3c9d
Timestamp: 1754884087 Timestamp [UCT]: 2025-08-11 03:48:07 Age [y:d:h:m:s]: 00:109:04:41:38
Block: 1344556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77287 RingCT/type: yes/0
Extra: 014887ac4072c78bf7e7a2a10a34c5a183fab652211da71ff50564821cf4df3c9d021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83eeccb6f3c42d1217d9cf8d889bb6b05f187f539f9f156fe86b43372f1c7672 0.600000000000 1832441 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": 1344566, "vin": [ { "gen": { "height": 1344556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83eeccb6f3c42d1217d9cf8d889bb6b05f187f539f9f156fe86b43372f1c7672" } } ], "extra": [ 1, 72, 135, 172, 64, 114, 199, 139, 247, 231, 162, 161, 10, 52, 197, 161, 131, 250, 182, 82, 33, 29, 167, 31, 245, 5, 100, 130, 28, 244, 223, 60, 157, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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