Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e43be3cef816a417d7f23e8fc2167f6300a182510929e835ea6f944e7e7c894c

Tx prefix hash: 0f599dc1c8a9ab6bd52f90d90f55c59e11a47b570cf2aaafd4025b9e87ee16b7
Tx public key: 268ca210526a7077e866951b0f6a946a64faf8286cb253719783ee39bf307797
Timestamp: 1705087628 Timestamp [UCT]: 2024-01-12 19:27:08 Age [y:d:h:m:s]: 01:356:17:55:23
Block: 933914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513861 RingCT/type: yes/0
Extra: 01268ca210526a7077e866951b0f6a946a64faf8286cb253719783ee39bf30779702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2144fb56957a6d77621eba16ca44ba91a80c8aab7e4c3fe07cfd758dcd06c02a 0.600000000000 1391898 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": 933924, "vin": [ { "gen": { "height": 933914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2144fb56957a6d77621eba16ca44ba91a80c8aab7e4c3fe07cfd758dcd06c02a" } } ], "extra": [ 1, 38, 140, 162, 16, 82, 106, 112, 119, 232, 102, 149, 27, 15, 106, 148, 106, 100, 250, 248, 40, 108, 178, 83, 113, 151, 131, 238, 57, 191, 48, 119, 151, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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