Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c8b89a9700368ff56bfef11b9baa110d044554d8b9d8138d8ec4fc42dac1c55

Tx prefix hash: 7fe32fd229d87c6ce7e5119f163de66ac2a6bda995d296d9346f9339cb1a0e67
Tx public key: c0db4b3f4a9a2c45c18e1472ebd46995513d4ab716896a77ecbe5b46e3c73d19
Timestamp: 1729585101 Timestamp [UCT]: 2024-10-22 08:18:21 Age [y:d:h:m:s]: 00:242:01:38:13
Block: 1136990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172687 RingCT/type: yes/0
Extra: 01c0db4b3f4a9a2c45c18e1472ebd46995513d4ab716896a77ecbe5b46e3c73d19021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2691c080a4b59063f34f4ff3886277370c6f7417f6402015b32a851e78ddacc4 0.600000000000 1620397 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": 1137000, "vin": [ { "gen": { "height": 1136990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2691c080a4b59063f34f4ff3886277370c6f7417f6402015b32a851e78ddacc4" } } ], "extra": [ 1, 192, 219, 75, 63, 74, 154, 44, 69, 193, 142, 20, 114, 235, 212, 105, 149, 81, 61, 74, 183, 22, 137, 106, 119, 236, 190, 91, 70, 227, 199, 61, 25, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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