Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d16df9bfb3a011e4f45043bf10d47f98d028860613a245eda3775154ac83d5

Tx prefix hash: 9eac05d8ed2a2daadeaa881b5c5219b22f5059143d94a791655368135f219d6e
Tx public key: fc07ad87a6a00384621eb7363c6344080eb153768e5d2df341dd024bc26a035b
Timestamp: 1576989137 Timestamp [UCT]: 2019-12-22 04:32:17 Age [y:d:h:m:s]: 05:012:04:26:27
Block: 29467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158300 RingCT/type: yes/0
Extra: 01fc07ad87a6a00384621eb7363c6344080eb153768e5d2df341dd024bc26a035b0211000000208a2ee0d9000000000000000000

1 output(s) for total of 490.190014045000 dcy

stealth address amount amount idx
00: b4c33695e555e43c8f2f87ae23dcfde45866e8e7d2eea6a887f716fef2a698f9 490.190014045000 48495 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": 29477, "vin": [ { "gen": { "height": 29467 } } ], "vout": [ { "amount": 490190014045, "target": { "key": "b4c33695e555e43c8f2f87ae23dcfde45866e8e7d2eea6a887f716fef2a698f9" } } ], "extra": [ 1, 252, 7, 173, 135, 166, 160, 3, 132, 98, 30, 183, 54, 60, 99, 68, 8, 14, 177, 83, 118, 142, 93, 45, 243, 65, 221, 2, 75, 194, 106, 3, 91, 2, 17, 0, 0, 0, 32, 138, 46, 224, 217, 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