Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39526fe0d1b28d6a198fe6445eea6b09b8e89feb48941da68de6bfb61ed3ddd0

Tx prefix hash: b3fcc678b99b900f09a8615f4c95ca11103ee0bbee4069f625472d9cbdf13e66
Tx public key: ebe19f2f0b1884a5ce38fd9c616e369dc82081375c531b58e5f34f2509dfba7a
Timestamp: 1683672038 Timestamp [UCT]: 2023-05-09 22:40:38 Age [y:d:h:m:s]: 01:333:12:04:32
Block: 756632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499575 RingCT/type: yes/0
Extra: 01ebe19f2f0b1884a5ce38fd9c616e369dc82081375c531b58e5f34f2509dfba7a02110000000833af99f4000000000000000000

1 output(s) for total of 1.909696203000 dcy

stealth address amount amount idx
00: f91aa34ad17e1a7dfaf99c6d34f19c40281905d0c4afd6a746a9d48e58b2aeae 1.909696203000 1205017 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": 756642, "vin": [ { "gen": { "height": 756632 } } ], "vout": [ { "amount": 1909696203, "target": { "key": "f91aa34ad17e1a7dfaf99c6d34f19c40281905d0c4afd6a746a9d48e58b2aeae" } } ], "extra": [ 1, 235, 225, 159, 47, 11, 24, 132, 165, 206, 56, 253, 156, 97, 110, 54, 157, 200, 32, 129, 55, 92, 83, 27, 88, 229, 243, 79, 37, 9, 223, 186, 122, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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