Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a7fed6595af60a8873e419ee77dd1b722f4fe4c95fc4683271aa89d8ec911f

Tx prefix hash: 11f3d0e62f3c290a4e8c1192a5f9fc5d6ead3c6fd3bae60a9a6d6f7bb33e5e38
Tx public key: bbae38ba7fbd1f6277e549959df034885563c7d53ce2160a1a10c312f632a0eb
Timestamp: 1705016204 Timestamp [UCT]: 2024-01-11 23:36:44 Age [y:d:h:m:s]: 01:096:06:15:43
Block: 933310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329921 RingCT/type: yes/0
Extra: 01bbae38ba7fbd1f6277e549959df034885563c7d53ce2160a1a10c312f632a0eb0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e2d2594e06f5539b708a96c5219529d6d6d9eef6c0693fb6592643a95702e0d 0.600000000000 1391272 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": 933320, "vin": [ { "gen": { "height": 933310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e2d2594e06f5539b708a96c5219529d6d6d9eef6c0693fb6592643a95702e0d" } } ], "extra": [ 1, 187, 174, 56, 186, 127, 189, 31, 98, 119, 229, 73, 149, 157, 240, 52, 136, 85, 99, 199, 213, 60, 226, 22, 10, 26, 16, 195, 18, 246, 50, 160, 235, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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