Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6bba75b990d0fcd1aeb2cc47a4fff250e740d3a52d42bee71ffdc13ad441f2e

Tx prefix hash: 097523f5b6711d97b2470954e466e009066e8190679749a38c7cb5ddcccebcd1
Tx public key: f614be1cbe07a73b90e9d937bb67a1c52407e3066f9350c56b53125e71d272a0
Timestamp: 1738571204 Timestamp [UCT]: 2025-02-03 08:26:44 Age [y:d:h:m:s]: 00:289:17:50:33
Block: 1211087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204852 RingCT/type: yes/0
Extra: 01f614be1cbe07a73b90e9d937bb67a1c52407e3066f9350c56b53125e71d272a0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59b894575fe5682afcb5f6897fb39614a3a0b69637acd1a7e02e833332737dbb 0.600000000000 1697846 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": 1211097, "vin": [ { "gen": { "height": 1211087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b894575fe5682afcb5f6897fb39614a3a0b69637acd1a7e02e833332737dbb" } } ], "extra": [ 1, 246, 20, 190, 28, 190, 7, 167, 59, 144, 233, 217, 55, 187, 103, 161, 197, 36, 7, 227, 6, 111, 147, 80, 197, 107, 83, 18, 94, 113, 210, 114, 160, 2, 17, 0, 0, 0, 3, 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