Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccafb5bd16cf63b1539c42af871ae435ec98b8d8dd27c3714c52fe4a4dc70858

Tx prefix hash: d2140af750b819a09f712b55765ee9264f6e63bfbf4a28148e1dd562c8fb8944
Tx public key: f1ab772efb4e56ea16eb7e79a55a7745fbec751cee069a04c3bbd63337a80b44
Timestamp: 1708424564 Timestamp [UCT]: 2024-02-20 10:22:44 Age [y:d:h:m:s]: 01:056:19:15:35
Block: 961593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301617 RingCT/type: yes/0
Extra: 01f1ab772efb4e56ea16eb7e79a55a7745fbec751cee069a04c3bbd63337a80b4402110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0a8a242a5692c51bf538a3512d29ab3a76ca9691200a0403c8dc5dcbc403d4b 0.600000000000 1421204 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": 961603, "vin": [ { "gen": { "height": 961593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0a8a242a5692c51bf538a3512d29ab3a76ca9691200a0403c8dc5dcbc403d4b" } } ], "extra": [ 1, 241, 171, 119, 46, 251, 78, 86, 234, 22, 235, 126, 121, 165, 90, 119, 69, 251, 236, 117, 28, 238, 6, 154, 4, 195, 187, 214, 51, 55, 168, 11, 68, 2, 17, 0, 0, 0, 14, 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