Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f954f447a0e4746c1fc0858de53b79bd71959636385462a1b7e2239dc4393e

Tx prefix hash: d5b7858d92e3870643a7bd31eeb534940f315a80dadbda412b2312915c255cc9
Tx public key: 3e4a243b5658951e488b557f8c9d04ade8e7f48a8996fc9aee9b468acdbdc5c4
Timestamp: 1702102094 Timestamp [UCT]: 2023-12-09 06:08:14 Age [y:d:h:m:s]: 01:120:13:10:35
Block: 909170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347291 RingCT/type: yes/0
Extra: 013e4a243b5658951e488b557f8c9d04ade8e7f48a8996fc9aee9b468acdbdc5c40211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc235120f5e2c2c08b43680880028ef0527d031d693d8ecfe99025d70f602fcc 0.600000000000 1366239 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": 909180, "vin": [ { "gen": { "height": 909170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc235120f5e2c2c08b43680880028ef0527d031d693d8ecfe99025d70f602fcc" } } ], "extra": [ 1, 62, 74, 36, 59, 86, 88, 149, 30, 72, 139, 85, 127, 140, 157, 4, 173, 232, 231, 244, 138, 137, 150, 252, 154, 238, 155, 70, 138, 205, 189, 197, 196, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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