Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb960d4857dd132b2b7caf0baea524c1ea843fe5f10a9c651a477427a5fb262

Tx prefix hash: d267529a552d20ccb5de4e5213833a127b47cceaf05b2628c6cfe2e0adb23012
Tx public key: 716256f1a3a260d2be70caecbb244b77ae87681e8583cb268396eedbb54b58ef
Timestamp: 1710266338 Timestamp [UCT]: 2024-03-12 17:58:58 Age [y:d:h:m:s]: 01:016:12:07:59
Block: 976865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272777 RingCT/type: yes/0
Extra: 01716256f1a3a260d2be70caecbb244b77ae87681e8583cb268396eedbb54b58ef02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b5877c38c8c66f29f58f5960c839860da440a5d9db3fa191a9ee4e7f30d90e1 0.600000000000 1436864 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": 976875, "vin": [ { "gen": { "height": 976865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b5877c38c8c66f29f58f5960c839860da440a5d9db3fa191a9ee4e7f30d90e1" } } ], "extra": [ 1, 113, 98, 86, 241, 163, 162, 96, 210, 190, 112, 202, 236, 187, 36, 75, 119, 174, 135, 104, 30, 133, 131, 203, 38, 131, 150, 238, 219, 181, 75, 88, 239, 2, 17, 0, 0, 0, 1, 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