Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38f80041b88016b6f04e2b4e9219306dd3ae9a3cce4e0d5bf16de0ee0d24310a

Tx prefix hash: 70139f82f909f14f11d49c39ff7ae992837082edbe474155694fbb54eee1ceb9
Tx public key: 68b4715418e18b2dc2577a8c6614e5018869e9be0cc6c1644e0107e988c35c3f
Timestamp: 1676749634 Timestamp [UCT]: 2023-02-18 19:47:14 Age [y:d:h:m:s]: 02:053:01:27:59
Block: 699866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559535 RingCT/type: yes/0
Extra: 0168b4715418e18b2dc2577a8c6614e5018869e9be0cc6c1644e0107e988c35c3f02110000000274b6d784000000000000000000

1 output(s) for total of 2.944783203000 dcy

stealth address amount amount idx
00: 249f5bc3f14956871b9c4d4c74d0b6a043823e10879497bef391bfbbb52efb0d 2.944783203000 1143289 of 0

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": 699876, "vin": [ { "gen": { "height": 699866 } } ], "vout": [ { "amount": 2944783203, "target": { "key": "249f5bc3f14956871b9c4d4c74d0b6a043823e10879497bef391bfbbb52efb0d" } } ], "extra": [ 1, 104, 180, 113, 84, 24, 225, 139, 45, 194, 87, 122, 140, 102, 20, 229, 1, 136, 105, 233, 190, 12, 198, 193, 100, 78, 1, 7, 233, 136, 195, 92, 63, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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