Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec055e8eb520d547e852c6f341fb47192bf6d542e39787b09ef9eca8b3b2908f

Tx prefix hash: 3eb105cc1fb10d4d17884c1dfd06600e5e21edef61d637c213235fa2b0633550
Tx public key: 08d5ef62a0d642826645a4aa995a576d5f1f5e89d98f9e55af5068bc10bf84b7
Timestamp: 1754584529 Timestamp [UCT]: 2025-08-07 16:35:29 Age [y:d:h:m:s]: 00:104:14:34:46
Block: 1342222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73852 RingCT/type: yes/0
Extra: 0108d5ef62a0d642826645a4aa995a576d5f1f5e89d98f9e55af5068bc10bf84b70211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f185fd2a5653238fafddeaa1ab1bd869251ed73b70c3293abe882cd53e4a781 0.600000000000 1830053 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": 1342232, "vin": [ { "gen": { "height": 1342222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f185fd2a5653238fafddeaa1ab1bd869251ed73b70c3293abe882cd53e4a781" } } ], "extra": [ 1, 8, 213, 239, 98, 160, 214, 66, 130, 102, 69, 164, 170, 153, 90, 87, 109, 95, 31, 94, 137, 217, 143, 158, 85, 175, 80, 104, 188, 16, 191, 132, 183, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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