Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ccfb8050e34af7b8a91ba713aca2efd3aca4250d0fef84aa9976d7bcbe8eff4

Tx prefix hash: 1f4cdb973caa35422e09a5c613cbc7370c5ef9e2d3c4a40962423f394501a51e
Tx public key: e171d32608eba2d928d2f8e3e2c2848ce5e9ca4ee4e34de70a4bbe5ee9cc48d7
Timestamp: 1674513810 Timestamp [UCT]: 2023-01-23 22:43:30 Age [y:d:h:m:s]: 01:357:08:12:50
Block: 681327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516388 RingCT/type: yes/0
Extra: 01e171d32608eba2d928d2f8e3e2c2848ce5e9ca4ee4e34de70a4bbe5ee9cc48d70211000000045029cbac000000000000000000

1 output(s) for total of 3.392194591000 dcy

stealth address amount amount idx
00: ff6542777ea1e15aa2c67b22dafabbe3f27f0d18e0c756edfcc2dad88d9feb1d 3.392194591000 1123414 of 0

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": 681337, "vin": [ { "gen": { "height": 681327 } } ], "vout": [ { "amount": 3392194591, "target": { "key": "ff6542777ea1e15aa2c67b22dafabbe3f27f0d18e0c756edfcc2dad88d9feb1d" } } ], "extra": [ 1, 225, 113, 211, 38, 8, 235, 162, 217, 40, 210, 248, 227, 226, 194, 132, 140, 229, 233, 202, 78, 228, 227, 77, 231, 10, 75, 190, 94, 233, 204, 72, 215, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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