Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357db4664a11212ac936e72f0cd439f8679605ea8bcc82f7ffd18f654b29205b

Tx prefix hash: a55b208489a407eef9007ee501aef738e387e5a7d246a7a1a93b576db3e8fdab
Tx public key: ea9eb56e69cbc15c58b244c78783fe9de44b6ba3bbfbade0d7c2e315b8cde241
Timestamp: 1711100368 Timestamp [UCT]: 2024-03-22 09:39:28 Age [y:d:h:m:s]: 00:357:21:11:05
Block: 983793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255880 RingCT/type: yes/0
Extra: 01ea9eb56e69cbc15c58b244c78783fe9de44b6ba3bbfbade0d7c2e315b8cde24102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8216a433d18579840b5da0fd2f2a74b07d72018cea6c789fd26f7209fe716062 0.600000000000 1443940 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": 983803, "vin": [ { "gen": { "height": 983793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8216a433d18579840b5da0fd2f2a74b07d72018cea6c789fd26f7209fe716062" } } ], "extra": [ 1, 234, 158, 181, 110, 105, 203, 193, 92, 88, 178, 68, 199, 135, 131, 254, 157, 228, 75, 107, 163, 187, 251, 173, 224, 215, 194, 227, 21, 184, 205, 226, 65, 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