Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 327d72a25050e70f3bc1295c51cbd8a1754d812d6ec86232369325bc9dae3b2f

Tx prefix hash: ec3477e3177268c651cb984767e7a27126c62f8c6a3e0b555fd6ce626e34663f
Tx public key: f0d9b8a562e2dde9cf486066f47ae1dd30c674282b900203ff6e531863b4e05d
Timestamp: 1581887948 Timestamp [UCT]: 2020-02-16 21:19:08 Age [y:d:h:m:s]: 05:059:11:22:56
Block: 66272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195607 RingCT/type: yes/0
Extra: 01f0d9b8a562e2dde9cf486066f47ae1dd30c674282b900203ff6e531863b4e05d021100000012d81c26c0000000000000000000

1 output(s) for total of 370.223732425000 dcy

stealth address amount amount idx
00: bdc9a83bab71ace87a6c1b2e1652ae54f88a712f9ea06504a0f28378385296ba 370.223732425000 122113 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": 66282, "vin": [ { "gen": { "height": 66272 } } ], "vout": [ { "amount": 370223732425, "target": { "key": "bdc9a83bab71ace87a6c1b2e1652ae54f88a712f9ea06504a0f28378385296ba" } } ], "extra": [ 1, 240, 217, 184, 165, 98, 226, 221, 233, 207, 72, 96, 102, 244, 122, 225, 221, 48, 198, 116, 40, 43, 144, 2, 3, 255, 110, 83, 24, 99, 180, 224, 93, 2, 17, 0, 0, 0, 18, 216, 28, 38, 192, 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