Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1337834cbf43e95cd7236d37e892df0236a0ac91cf37032d57c5b90bb9d0c16e

Tx prefix hash: f2383b2b346cf40bf82e6b60eecd88b4db6b42007c69530f59995d91c8f2baec
Tx public key: 3ffa25bfa34fbc701d38e392850fd17117129fa8f295f0c7ca5a84a5cbd1c82b
Timestamp: 1760979283 Timestamp [UCT]: 2025-10-20 16:54:43 Age [y:d:h:m:s]: 00:024:17:51:39
Block: 1394197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17696 RingCT/type: yes/0
Extra: 013ffa25bfa34fbc701d38e392850fd17117129fa8f295f0c7ca5a84a5cbd1c82b02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507ec76b1547da7cc1a8780d3eead5f7fc9a53463d428aa530b72e27f4a7f3b9 0.600000000000 1882464 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": 1394207, "vin": [ { "gen": { "height": 1394197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507ec76b1547da7cc1a8780d3eead5f7fc9a53463d428aa530b72e27f4a7f3b9" } } ], "extra": [ 1, 63, 250, 37, 191, 163, 79, 188, 112, 29, 56, 227, 146, 133, 15, 209, 113, 23, 18, 159, 168, 242, 149, 240, 199, 202, 90, 132, 165, 203, 209, 200, 43, 2, 17, 0, 0, 0, 3, 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