Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a2cc4ae124059d26f04db19fa48c6ea15a0e2eb0e51f91a686b4638525a684

Tx prefix hash: c8529104ad07b0d7806d057e2fce821d6f56ae01e1388f4a3ec59a9bab87ae10
Tx public key: 1bd2938dceef99a4af0a879509ad10869a4ab5ce2994144ae11172ed2a1b059b
Timestamp: 1718108183 Timestamp [UCT]: 2024-06-11 12:16:23 Age [y:d:h:m:s]: 00:141:03:01:41
Block: 1041884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101000 RingCT/type: yes/0
Extra: 011bd2938dceef99a4af0a879509ad10869a4ab5ce2994144ae11172ed2a1b059b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2b269f11d5e6d79ed751aa8a84b34eed876f3abeebac286e7dfa023473217a7 0.600000000000 1510663 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": 1041894, "vin": [ { "gen": { "height": 1041884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2b269f11d5e6d79ed751aa8a84b34eed876f3abeebac286e7dfa023473217a7" } } ], "extra": [ 1, 27, 210, 147, 141, 206, 239, 153, 164, 175, 10, 135, 149, 9, 173, 16, 134, 154, 74, 181, 206, 41, 148, 20, 74, 225, 17, 114, 237, 42, 27, 5, 155, 2, 17, 0, 0, 0, 2, 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