Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a203e0a5c575f67fb98fb91ed05d6741b978a32d6d690cddaec2d91edef568a4

Tx prefix hash: e36ad2c03833a3d9371c5be5f4cca1befe77924b9197e47d450674fe93d67ec5
Tx public key: 7ae3fe67aa15f6d84c1949ea2298e4bd9eaf7c35d83aee1898793bedd9ea7333
Timestamp: 1707287911 Timestamp [UCT]: 2024-02-07 06:38:31 Age [y:d:h:m:s]: 01:021:06:18:11
Block: 952161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276224 RingCT/type: yes/0
Extra: 017ae3fe67aa15f6d84c1949ea2298e4bd9eaf7c35d83aee1898793bedd9ea73330211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 937d48c20fc0d17ed41d64837bf0cae01d23dbb95667b7c8579f617fa43ebf82 0.600000000000 1411041 of 15

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": 952171, "vin": [ { "gen": { "height": 952161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "937d48c20fc0d17ed41d64837bf0cae01d23dbb95667b7c8579f617fa43ebf82" } } ], "extra": [ 1, 122, 227, 254, 103, 170, 21, 246, 216, 76, 25, 73, 234, 34, 152, 228, 189, 158, 175, 124, 53, 216, 58, 238, 24, 152, 121, 59, 237, 217, 234, 115, 51, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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