Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d300abf412e1d26776a0702b9083380c57e94a5494c9c0ec5ebc30eafb741a

Tx prefix hash: bd12d60c78f21954a255b7db734b254085530c46921fb6cf36c496f888ee3da9
Tx public key: f8e87b1d8c279d0efb48fb4f9bd9a1fd121c4047a830ee119fe0b2b63567ee07
Timestamp: 1676887729 Timestamp [UCT]: 2023-02-20 10:08:49 Age [y:d:h:m:s]: 01:207:02:33:20
Block: 701009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408924 RingCT/type: yes/0
Extra: 01f8e87b1d8c279d0efb48fb4f9bd9a1fd121c4047a830ee119fe0b2b63567ee07021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.919215069000 dcy

stealth address amount amount idx
00: fc8c7d7edf5cb95eae93696a2b2aaaf05c9a205f3c6c966fb87c98f2e68e9564 2.919215069000 1144468 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": 701019, "vin": [ { "gen": { "height": 701009 } } ], "vout": [ { "amount": 2919215069, "target": { "key": "fc8c7d7edf5cb95eae93696a2b2aaaf05c9a205f3c6c966fb87c98f2e68e9564" } } ], "extra": [ 1, 248, 232, 123, 29, 140, 39, 157, 14, 251, 72, 251, 79, 155, 217, 161, 253, 18, 28, 64, 71, 168, 48, 238, 17, 159, 224, 178, 182, 53, 103, 238, 7, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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