Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f82ab3bd7d209c34e819883ab59f14abbbb83561b72c24b78632b1f72f27256

Tx prefix hash: 4308b2c7e721fe3445b975f1165b0369cb4cabd4a1e37aaf3bec88728f7fd7ee
Tx public key: 9978b1f2e2a0095731e7ea4bcfe64d34c1208a46cb6af159b681bb248e0c88f0
Timestamp: 1736906467 Timestamp [UCT]: 2025-01-15 02:01:07 Age [y:d:h:m:s]: 00:155:23:17:04
Block: 1197564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111163 RingCT/type: yes/0
Extra: 019978b1f2e2a0095731e7ea4bcfe64d34c1208a46cb6af159b681bb248e0c88f0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7936de412cea00b8c4ebfc4ba6fa6156ef3bb30aa945e2c090ed3e1cefc96272 0.600000000000 1684177 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": 1197574, "vin": [ { "gen": { "height": 1197564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7936de412cea00b8c4ebfc4ba6fa6156ef3bb30aa945e2c090ed3e1cefc96272" } } ], "extra": [ 1, 153, 120, 177, 242, 226, 160, 9, 87, 49, 231, 234, 75, 207, 230, 77, 52, 193, 32, 138, 70, 203, 106, 241, 89, 182, 129, 187, 36, 142, 12, 136, 240, 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