Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b636e9519faa01cec57a7e5e2432c4e949247d6bfbe0bb0cdc4b5f04b52644bb

Tx prefix hash: c96898b01d1e00e1fc25bf920a2cd85e32f37bac28707ca8e65a9e057b5a887a
Tx public key: 4fa5568deafe80055dffdeae0547950b048843f6e3e2ba1a6d655405fae1d47a
Timestamp: 1722095351 Timestamp [UCT]: 2024-07-27 15:49:11 Age [y:d:h:m:s]: 00:281:08:43:03
Block: 1074928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201007 RingCT/type: yes/0
Extra: 014fa5568deafe80055dffdeae0547950b048843f6e3e2ba1a6d655405fae1d47a021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67b2b66e12a59caa013343c7b37025c14efea341f2393ef4cbf047ff6f25d468 0.600000000000 1547447 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": 1074938, "vin": [ { "gen": { "height": 1074928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67b2b66e12a59caa013343c7b37025c14efea341f2393ef4cbf047ff6f25d468" } } ], "extra": [ 1, 79, 165, 86, 141, 234, 254, 128, 5, 93, 255, 222, 174, 5, 71, 149, 11, 4, 136, 67, 246, 227, 226, 186, 26, 109, 101, 84, 5, 250, 225, 212, 122, 2, 17, 0, 0, 0, 19, 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