Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dfeb23c0bc957f984ab56ad3eb9f2ead3ef426811abfa0daebbd47d4800c865

Tx prefix hash: 31a9373d0a31ac9a7213c4babdec10a10a766e8e90808a7e2e8ddca2a2f90a5a
Tx public key: c9c37e4ed22da894ad64a1d3c1b84731f66d890e60cfb0be68bff3bfb8e50ff0
Timestamp: 1582193494 Timestamp [UCT]: 2020-02-20 10:11:34 Age [y:d:h:m:s]: 04:349:01:43:32
Block: 68700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141775 RingCT/type: yes/0
Extra: 01c9c37e4ed22da894ad64a1d3c1b84731f66d890e60cfb0be68bff3bfb8e50ff0021100000001c71d3ff9000000000000000000

1 output(s) for total of 363.386832896000 dcy

stealth address amount amount idx
00: 0b0d95b5f680d6b0d27a2bd44d52ff804aef563241c8f6f049c5eec79e7b7703 363.386832896000 126661 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": 68710, "vin": [ { "gen": { "height": 68700 } } ], "vout": [ { "amount": 363386832896, "target": { "key": "0b0d95b5f680d6b0d27a2bd44d52ff804aef563241c8f6f049c5eec79e7b7703" } } ], "extra": [ 1, 201, 195, 126, 78, 210, 45, 168, 148, 173, 100, 161, 211, 193, 184, 71, 49, 246, 109, 137, 14, 96, 207, 176, 190, 104, 191, 243, 191, 184, 229, 15, 240, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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