Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9cc066a53d730b02c875b4feddaee678b9782e42c32d9d551e6df2d6bdf8611

Tx prefix hash: de97763ce8139cf1e0abdc8758948295f41409e13e0a04710f54935118a2aaf6
Tx public key: 4823b08de81f2d7b7843b372aa8b73130318012f4ebb7223eb14cb14c40d419e
Timestamp: 1721721027 Timestamp [UCT]: 2024-07-23 07:50:27 Age [y:d:h:m:s]: 00:252:17:17:18
Block: 1071817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180524 RingCT/type: yes/0
Extra: 014823b08de81f2d7b7843b372aa8b73130318012f4ebb7223eb14cb14c40d419e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 900774cb94ef37bbe0b317a3e5470e0224f4df369508fcc796c36955c240a7d6 0.600000000000 1544184 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": 1071827, "vin": [ { "gen": { "height": 1071817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "900774cb94ef37bbe0b317a3e5470e0224f4df369508fcc796c36955c240a7d6" } } ], "extra": [ 1, 72, 35, 176, 141, 232, 31, 45, 123, 120, 67, 179, 114, 170, 139, 115, 19, 3, 24, 1, 47, 78, 187, 114, 35, 235, 20, 203, 20, 196, 13, 65, 158, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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