Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c04fe79974fbd05f446f4c2d13cd5b52f204fc9b254c2d923a4824d72e7ea6

Tx prefix hash: b94382fe33cba0f675c6c9562af39c1954f25d1286706c7cbaa9d78671f25c5f
Tx public key: af18070bc4d0f69efdbcec861ffb606cc83df2a9a636d3a9591ea78aa4e810e4
Timestamp: 1582055792 Timestamp [UCT]: 2020-02-18 19:56:32 Age [y:d:h:m:s]: 04:319:01:02:10
Block: 67719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120404 RingCT/type: yes/0
Extra: 01af18070bc4d0f69efdbcec861ffb606cc83df2a9a636d3a9591ea78aa4e810e40211000000484ac5aa02000000000000000000

1 output(s) for total of 366.116792176000 dcy

stealth address amount amount idx
00: 76d4b35eaabb151be8b4be877938f609aa02ce248a78dc73f4a01f95a021b8ab 366.116792176000 124718 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": 67729, "vin": [ { "gen": { "height": 67719 } } ], "vout": [ { "amount": 366116792176, "target": { "key": "76d4b35eaabb151be8b4be877938f609aa02ce248a78dc73f4a01f95a021b8ab" } } ], "extra": [ 1, 175, 24, 7, 11, 196, 208, 246, 158, 253, 188, 236, 134, 31, 251, 96, 108, 200, 61, 242, 169, 166, 54, 211, 169, 89, 30, 167, 138, 164, 232, 16, 228, 2, 17, 0, 0, 0, 72, 74, 197, 170, 2, 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