Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef0ed8fa117f10a28b716c08bd75a647b8a5c88b59af43d90fa0704b7b298305

Tx prefix hash: 72b3bef2310cd0fb981aabb79ab833a6ebbf94d08997ae8a4bd0db6cfcc214a2
Tx public key: eb8d115289141cd568620e7d96b4c5b649091bdcde245a5d5df6a8a72115f0f1
Timestamp: 1742476908 Timestamp [UCT]: 2025-03-20 13:21:48 Age [y:d:h:m:s]: 00:242:03:19:49
Block: 1243448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170762 RingCT/type: yes/0
Extra: 01eb8d115289141cd568620e7d96b4c5b649091bdcde245a5d5df6a8a72115f0f1021100000006bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ea37c75cfdcd394524ad87be7e699ee5f942fff1718b8d4158572b0925b03b 0.600000000000 1730433 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": 1243458, "vin": [ { "gen": { "height": 1243448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ea37c75cfdcd394524ad87be7e699ee5f942fff1718b8d4158572b0925b03b" } } ], "extra": [ 1, 235, 141, 17, 82, 137, 20, 28, 213, 104, 98, 14, 125, 150, 180, 197, 182, 73, 9, 27, 220, 222, 36, 90, 93, 93, 246, 168, 167, 33, 21, 240, 241, 2, 17, 0, 0, 0, 6, 191, 167, 118, 35, 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