Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ba2d22a50fd552c5e7a7fc56140fb32e44a8b73a005e251b4782b4f82fca55a

Tx prefix hash: 3b7a1082616f0600a601d14a69dc69401a9b500773ad98b2150cea5002e9e2af
Tx public key: e9a46545a6cd9fea1c6d3c78ebe9ebdd1d45276698e2ea64084e4bac233f1982
Timestamp: 1736176735 Timestamp [UCT]: 2025-01-06 15:18:55 Age [y:d:h:m:s]: 00:303:10:31:58
Block: 1191549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214332 RingCT/type: yes/0
Extra: 01e9a46545a6cd9fea1c6d3c78ebe9ebdd1d45276698e2ea64084e4bac233f1982021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b50626827b98ca655ea011df750a9bcc358ec35e4e8ee1a16fc7b64c1e876b0 0.600000000000 1678088 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": 1191559, "vin": [ { "gen": { "height": 1191549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b50626827b98ca655ea011df750a9bcc358ec35e4e8ee1a16fc7b64c1e876b0" } } ], "extra": [ 1, 233, 164, 101, 69, 166, 205, 159, 234, 28, 109, 60, 120, 235, 233, 235, 221, 29, 69, 39, 102, 152, 226, 234, 100, 8, 78, 75, 172, 35, 63, 25, 130, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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