Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684b28b5557b5699dbb594ae879618961f23eb8ba1f906ede1b803624734abae

Tx prefix hash: c2cbba23e20072426bad04ee4c9750f872105a3a2cf8469ce280fb4118d5500c
Tx public key: dac9e9d053412228b4c1d69eb8089499337a67c0e171922447d8f6cb3f4db1cb
Timestamp: 1751657291 Timestamp [UCT]: 2025-07-04 19:28:11 Age [y:d:h:m:s]: 00:127:23:26:16
Block: 1318795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89760 RingCT/type: yes/0
Extra: 01dac9e9d053412228b4c1d69eb8089499337a67c0e171922447d8f6cb3f4db1cb02110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdca39acdedea99fb7d8653df8c41dfbce501ba5df9a9c89de5a13f52e49a6bb 0.600000000000 1806482 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": 1318805, "vin": [ { "gen": { "height": 1318795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdca39acdedea99fb7d8653df8c41dfbce501ba5df9a9c89de5a13f52e49a6bb" } } ], "extra": [ 1, 218, 201, 233, 208, 83, 65, 34, 40, 180, 193, 214, 158, 184, 8, 148, 153, 51, 122, 103, 192, 225, 113, 146, 36, 71, 216, 246, 203, 63, 77, 177, 203, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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